Methods and systems for managing cochlear implant fitting software features

ABSTRACT

An exemplary method of managing cochlear implant fitting software includes a cochlear implant fitting subsystem maintaining data representative of a cochlear implant fitting software package comprising a plurality of cochlear implant fitting features, maintaining data representative of a plurality of independent licensing heuristics corresponding to the plurality of cochlear implant fitting features, and selectively enabling or disabling each cochlear implant fitting feature within the plurality of cochlear implant fitting features in accordance with the corresponding independent licensing heuristic. Corresponding methods and systems are also described.

BACKGROUND INFORMATION

The natural sense of hearing in human beings involves the use of haircells in the cochlea that convert or transduce acoustic signals intoauditory nerve impulses. Hearing loss, which may be due to manydifferent causes, is generally of two types: conductive andsensorineural. Conductive hearing loss occurs when the normal mechanicalpathways for sound to reach the hair cells in the cochlea are impeded.These sound pathways may be impeded, for example, by damage to theauditory ossicles. Conductive hearing loss may often be overcome throughthe use of conventional hearing aids that amplify sound so that acousticsignals can reach the hair cells within the cochlea. Some types ofconductive hearing loss may also be treated by surgical procedures.

Sensorineural hearing loss, on the other hand, is caused by the absenceor destruction of the hair cells in the cochlea, which are needed totransduce acoustic signals into auditory nerve impulses. People whosuffer from sensorineural hearing loss may be unable to derivesignificant benefit from conventional hearing aid systems, no matter howloud the acoustic stimulus. This is because the mechanism fortransducing sound energy into auditory nerve impulses has been damaged.Thus, in the absence of properly functioning hair cells, auditory nerveimpulses cannot be generated directly from sounds.

To overcome sensorineural hearing loss, numerous cochlear implantsystems—or cochlear prostheses—have been developed. Cochlear implantsystems bypass the hair cells in the cochlea by presenting electricalstimulation directly to the auditory nerve fibers by way of one or morechannels formed by an array of electrodes implanted in the cochlea.Direct stimulation of the auditory nerve fibers leads to the perceptionof sound in the brain and at least partial restoration of hearingfunction.

When a cochlear implant system is initially implanted in a patient, andduring follow-up tests and checkups thereafter, it is usually necessaryto “fit” the cochlear implant system to the patient. Fitting of acochlear implant system to a patient is typically performed by anaudiologist or the like who presents various stimuli to the patient andrelies on subjective feedback from the patient as to how such stimuliare perceived. Adjustments may be made to specifically tailor theparameters of the cochlear implant system to the patient being fitted.

Fitting a cochlear implant system to a patient typically utilizes and/oris performed by cochlear implant fitting hardware that implements and/oroperates in accordance with cochlear implant fitting software. Likeother medical-related products, cochlear implant fitting software isregulated by governmental agencies from geographic regions (e.g.,countries, states, provinces, etc.) where the cochlear implant fittingsoftware is released. Because the regulation of the fitting software maydiffer from one geographic region to the next, it may be necessaryproduce several different versions of the cochlear implant fittingsoftware, with each different version corresponding to the specificregulations/limitations of a particular geographic region. However, theprocess of creating, testing, debugging, releasing, and managingmultiple versions of cochlear implant fitting software can be burdensomeand expensive. This problem is further exacerbated by the fact that eachversion of the cochlear implant fitting software must pass through aregulatory approval process.

SUMMARY

An exemplary method of managing cochlear implant fitting softwareincludes a cochlear implant fitting subsystem 1) maintaining datarepresentative of a cochlear implant fitting software package comprisinga plurality of cochlear implant fitting features, 2) maintaining datarepresentative of a plurality of independent licensing heuristicscorresponding to the plurality of cochlear implant fitting features, and3) selectively enabling or disabling each cochlear implant fittingfeature in accordance with the corresponding independent licensingheuristic.

Another exemplary method of managing cochlear implant fitting softwareincludes a cochlear implant fitting subsystem 1) maintaining datarepresentative of a cochlear implant fitting software package comprisinga plurality of cochlear implant fitting features, 2) maintaining datarepresentative of a plurality of independent licensing heuristicscorresponding to the plurality of cochlear implant fitting features, 3)detecting a satisfaction of one or more licensing conditions specifiedby a particular independent licensing heuristic corresponding to aparticular cochlear implant fitting feature, 4) enabling the particularcochlear implant fitting feature in response to the detecting thesatisfaction of the one or more licensing conditions, and 5) performingone or more cochlear implant fitting operations in accordance with theparticular cochlear implant fitting feature.

An exemplary system for managing cochlear implant fitting softwareincludes 1) a storage facility configured to maintain datarepresentative of a cochlear implant fitting software package comprisinga plurality of cochlear implant fitting features and maintain datarepresentative of a plurality of independent licensing heuristicscorresponding to the plurality of cochlear implant fitting features, and2) a feature control facility communicatively coupled to the storagefacility and configured to selectively enable or disable each cochlearimplant fitting feature in accordance with the corresponding independentlicensing heuristic.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings illustrate various embodiments and are a partof the specification. The illustrated embodiments are merely examplesand do not limit the scope of the disclosure. Throughout the drawings,identical or similar reference numbers designate identical or similarelements.

FIG. 1 illustrates an exemplary cochlear implant system according toprinciples described herein.

FIG. 2 illustrates an exemplary cochlear implant fitting systemaccording to principles described herein.

FIG. 3 illustrates exemplary components of an exemplary fittingsubsystem according to principles described herein.

FIG. 4 illustrates exemplary components of an exemplary sound processoraccording to principles described herein.

FIG. 5 illustrates an exemplary implementation of the cochlear implantfitting system of FIG. 2 according to principles described herein.

FIG. 6 illustrates an exemplary method of managing cochlear implantfitting software according to principles described herein.

FIG. 7 illustrates an exemplary cochlear implant fitting softwarepackage according to principles described herein.

FIG. 8 shows an exemplary graphical user interface (“GUI”) that may bepresented for display according to principles described herein.

FIG. 9 illustrates an exemplary cochlear implant patient being fitted bythe fitting components of FIG. 5 according to principles describedherein.

FIG. 10 illustrates another exemplary method of managing cochlearimplant fitting software according to principles described herein.

FIG. 11 illustrates an exemplary computing device according toprinciples described herein.

DETAILED DESCRIPTION

Methods and systems for managing cochlear implant fitting software aredescribed herein. As described in more detail below, a cochlear implantfitting subsystem may be configured to maintain data representative of acochlear implant fitting software package comprising a plurality ofcochlear implant fitting features. The cochlear implant fittingsubsystem may also be configured to maintain data representative of aplurality of independent licensing heuristics corresponding to theplurality of cochlear implant fitting features. For example, eachindependent licensing heuristic within the plurality of independentlicensing heuristics may correspond to a different cochlear implantfitting feature within the plurality of cochlear implant fittingfeatures. In addition, the cochlear implant fitting subsystem may beconfigured to selectively enable or disable each cochlear implantfitting feature in accordance with the corresponding independentlicensing heuristic.

As used herein, the term “cochlear implant fitting feature” or “fittingfeature” refers to any feature, option, tool, program, and/or functionassociated with the fitting of a cochlear implant system to a patient.For example, cochlear implant fitting features may include features,options, tools, programs, and/or functions associated with one or moresound processing operations, fitting operations, diagnostic operations,measurement operations, stimulation operations, neural responsedetection operations, control operations, and/or any other suitableoperations of a cochlear implant fitting subsystem and/or cochlearimplant system.

Numerous advantages may be associated with the methods and systemsdescribed herein. For example, a cochlear implant fitting softwaredeveloper may create, test, release, and/or distribute a single cochlearimplant fitting software package for use by a plurality of differentcochlear implant fitting subsystems across a plurality of differentgeographic regions (e.g., countries, states, provinces, etc.) regardlessof variances in regulatory restrictions and/or other limitations placedon the cochlear implant fitting software from one cochlear implantfitting subsystem and/or geographic region to the next. Thereafter, eachcochlear implant fitting subsystem may selectively enable or disableeach cochlear implant fitting feature of the software package inaccordance with specific information associated with the fittingsubsystem (e.g., a geographic location of the cochlear implant fittingsubsystem, an association of the cochlear implant fitting subsystem witha clinical trial, a particular license purchased by a user of thecochlear implant fitting subsystem, etc.), and may thereby controlaccess to one or more features of the software package on afeature-by-feature basis. As a result, the methods and systems describedherein allow a cochlear implant fitting software developer to moreeasily and effectively manage the distribution and/or use of itscochlear implant fitting software.

To facilitate an understanding of the methods and systems describedherein, an exemplary cochlear implant system 100 will be described inconnection with FIG. 1. As shown in FIG. 1, cochlear implant system 100may include a microphone 102, a sound processor 104, a headpiece 106having a coil 108 disposed therein, a cochlear implant 110 (alsoreferred to as an “implantable cochlear stimulator”), and a lead 112with a plurality of electrodes 114 disposed thereon. Additional oralternative components may be included within cochlear implant system100 as may serve a particular implementation.

As shown in FIG. 1, microphone 102, sound processor 104, and headpiece106 may be located external to a cochlear implant patient. In somealternative examples, microphone 102 and/or sound processor 104 may beimplanted within the patient. In such configurations, the need forheadpiece 106 may be obviated.

Microphone 102 may detect an audio signal and convert the detectedsignal to a corresponding electrical signal. The electrical signal maybe sent from microphone 102 to sound processor 104 via a communicationlink 116, which may include a telemetry link, a wire, and/or any othersuitable communication link.

Sound processor 104 is configured to direct cochlear implant 110 togenerate and apply electrical stimulation (also referred to herein as“stimulation current”) to one or more stimulation sites within a cochleaof the patient. To this end, sound processor 104 may process the audiosignal detected by microphone 102 in accordance with a selected soundprocessing strategy to generate appropriate stimulation parameters forcontrolling cochlear implant 110. Sound processor 104 may include or beimplemented by a behind-the-ear (“BTE”) unit, a portable speechprocessor (“PSP”), and/or any other sound-processing unit as may serve aparticular implementation. Exemplary components of sound processor 104will be described in more detail below.

Sound processor 104 may be configured to transcutaneously transmit, inaccordance with a sound processing program associated with cochlearimplant 110, one or more control parameters and/or one or more powersignals to cochlear implant 110 with coil 108 by way of a communicationlink 118. These control parameters may be configured to specify one ormore stimulation parameters, operating parameters, and/or any otherparameter by which cochlear implant 110 is to operate as may serve aparticular implementation. Exemplary control parameters include, but arenot limited to, stimulation current levels, volume control parameters,program selection parameters, operational state parameters (e.g.,parameters that turn a sound processor and/or a cochlear implant on oroff), audio input source selection parameters, fitting parameters, noisereduction parameters, microphone sensitivity parameters, microphonedirection parameters, pitch parameters, timbre parameters, sound qualityparameters, most comfortable current levels (“M levels”), thresholdcurrent levels (“T levels”), channel acoustic gain parameters, front andbackend dynamic range parameters, current steering parameters, pulserate values, pulse width values, frequency parameters, amplitudeparameters, waveform parameters, electrode polarity parameters (i.e.,anode-cathode assignment), location parameters (i.e., which electrodepair or electrode group receives the stimulation current), stimulationtype parameters (i.e., monopolar, bipolar, or tripolar stimulation),burst pattern parameters (e.g., burst on time and burst off time), dutycycle parameters, spectral tilt parameters, filter parameters, anddynamic compression parameters. Sound processor 104 may also beconfigured to operate in accordance with one or more of the controlparameters.

As shown in FIG. 1, coil 108 may be housed within headpiece 106, whichmay be affixed to a patient's head and positioned such that coil 108 iscommunicatively coupled to a corresponding coil included within cochlearimplant 110. In this manner, control parameters and power signals may bewirelessly transmitted between sound processor 104 and cochlear implant110 via communication link 118. It will be understood that datacommunication link 118 may include a bi-directional communication linkand/or one or more dedicated uni-directional communication links. Insome alternative embodiments, sound processor 104 and cochlear implant110 may be directly connected with one or more wires or the like.

Cochlear implant 110 may be configured to generate electricalstimulation representative of an audio signal detected by microphone 102in accordance with one or more stimulation parameters transmittedthereto by sound processor 104. Cochlear implant 110 may be furtherconfigured to apply the electrical stimulation to one or morestimulation sites within the cochlea via one or more electrodes 114disposed along lead 112. In some examples, cochlear implant 110 mayinclude a plurality of independent current sources, each associated witha channel defined by one or more of electrodes 114. In this manner,different stimulation current levels may be applied to differentstimulation sites simultaneously by way of multiple electrodes 114. Insuch examples, cochlear implant system 100 may be referred to as a“multi-channel cochlear implant system.”

To facilitate application of the electrical stimulation generated bycochlear implant 110, lead 112 may be inserted within a duct of thecochlea such that electrodes 114 are in communication with one or morestimulation sites within the cochlea. As used herein, the term “incommunication with” refers to electrodes 114 being adjacent to, in thegeneral vicinity of, in close proximity to, directly next to, ordirectly on the stimulation site. Any number of electrodes 114 (e.g.,sixteen) may be disposed on lead 112 as may serve a particularimplementation.

FIG. 2 illustrates an exemplary cochlear implant fitting system 200 (orsimply “fitting system 200”) that may be used to fit sound processor 104to a patient. As used herein, the terms “fitting a sound processor to apatient” and “fitting a cochlear implant to a patient” will be usedinterchangeably to refer to performing one or more fitting operationsassociated with sound processor 104, cochlear implant 110, and/or anyother component of cochlear implant system 100. Such fitting operationsmay include, but are not limited to, adjusting one or more controlparameters by which sound processor 104 and/or cochlear implant 110operate, measuring one or more electrode impedances, performing one ormore neural response detection operations, and/or performing one or morediagnostics procedures associated with cochlear implant system 100.

As shown in FIG. 2, fitting system 200 may include a cochlear implantfitting subsystem 202 (or simply “fitting subsystem 202”) configured tobe selectively and communicatively coupled to sound processor 104 ofcochlear implant system 100 by way of a communication link 204. Fittingsubsystem 202 and sound processor 104 may communicate using any suitablecommunication technologies, devices, networks, media, and protocolssupportive of data communications.

Fitting subsystem 202 may be configured to perform one or more of thefitting operations described herein. To this end, fitting subsystem 202may be implemented by any suitable combination of computing andcommunication devices including, but not limited to, a fitting station,a personal computer, a laptop computer, a handheld device, a mobiledevice (e.g., a mobile phone), a clinician's programming interface(“CPI”) device, and/or any other suitable component as may serve aparticular implementation.

FIG. 3 illustrates exemplary components of fitting subsystem 202. Asshown in FIG. 3, fitting subsystem 202 may include a communicationfacility 302, a user interface facility 304, a fitting facility 306, afeature control facility 308, and a storage facility 310, which may becommunicatively coupled to one another using any suitable communicationtechnologies. Each of these facilities will now be described in moredetail.

Communication facility 302 may be configured to facilitate communicationbetween fitting subsystem 202 and sound processor 104. For example,communication facility 302 may be implemented by a CPI device, which mayinclude any suitable combination of components configured to allowfitting subsystem 202 to interface and communicate with sound processor104. Communication facility 302 may additionally or alternativelyinclude one or more transceiver components configured to wirelesslytransmit data (e.g., program data and/or control parameter data) tosound processor 104 and/or wirelessly receive data (e.g., feedback data,impedance measurement data, neural response data, etc.) from soundprocessor 104.

Communication facility 302 may be further configured to selectivelycommunicate with cochlear implant 110 by way of sound processor 104during a fitting process. For example, communication facility 302 may beconfigured to communicate with cochlear implant 110 when sound processor104 is communicatively coupled (e.g., “locked”) to cochlear implant 110.

Communication facility 302 may additionally or alternatively beconfigured to facilitate communication between fitting subsystem 302 andone or more other devices. For example, communication facility 302 maybe configured to facilitate communication between fitting subsystem 302and one or more computing devices (e.g., by way of the Internet and/orone or more other types of networks), reference implants, and/or anyother computing device as may serve a particular implementation.

User interface facility 304 may be configured to provide one or moreuser interfaces configured to facilitate user interaction with fittingsubsystem 202. For example, user interface facility 304 may provide agraphical user interface (“GUI”) through which one or more cochlearimplant fitting features described herein may be used by a user andthrough which user input may be received from the user. User interfacefacility 304 may be configured to provide the GUI to a display device(e.g., a computer monitor) for display. In some examples, the GUI maydisplay information associated with a cochlear implant fitting softwarepackage (e.g., the GUI may display information associated with one ormore cochlear implant fitting features included in the cochlear implantfitting software package). Additionally or alternatively, user interfacefacility 304 may be configured to facilitate the use and/or managementof the cochlear implant fitting software package by way of the GUI, aswill be explained in more detail below.

Fitting facility 306 may be configured to perform one or more of thefitting operations described herein. For example, fitting facility 306may be configured to adjust one or more control parameters by whichsound processor 104 and/or cochlear implant 110 operate, direct soundprocessor 104 to measure one or more electrode impedances, perform oneor more neural response detection operations, and/or perform one or morediagnostics procedures associated with cochlear implant system 100.

In some examples, fitting facility 306 may be configured to perform oneor more fitting operations in accordance with a cochlear implant fittingsoftware package. For example, fitting facility 306 may be configured toperform the one or more fitting operations using one or more cochlearimplant fitting features included within the cochlear implant fittingsoftware package, as will be explained in more detail below.

In some examples, fitting facility 306 may be configured to initializesound processor 104 prior to using sound processor 104 to fit cochlearimplant 110 to a patient. Such initialization may include, but is notlimited to, associating sound processor 104 with a particular patient(e.g., associating sound processor 104 with patient-specific fittingdata), associating sound processor 104 with a particular cochlearimplant 110, loading data onto sound processor 104, clearing data fromsound processor 104, and/or otherwise preparing sound processor 104 fora fitting session in which sound processor 104 is to be fitted to apatient.

Feature control facility 308 may be configured to selectively enable ordisable one or more cochlear implant fitting features included within acochlear implant fitting software package. For example, an exemplarycochlear implant fitting software package may include a plurality ofcochlear implant fitting features. The plurality of cochlear implantfitting features may correspond to a plurality of independent licensingheuristics. For example, each of the plurality of independent licensingheuristics may correspond to a different cochlear implant fittingfeature. The independent licensing heuristics may be configured togovern the enablement or disablement of the corresponding cochlearimplant fitting features. For example, each independent licensingheuristic may specify one or more licensing conditions to be satisfiedin order for the corresponding cochlear implant fitting feature to beenabled.

The independent licensing heuristics may specify any suitable licensingconditions as may serve a particular implementation. For example, anexemplary licensing condition may be associated with a geographic region(e.g., the licensing condition may require that fitting subsystem 202 bephysically located within a particular country), a clinical trial (e.g.,the licensing condition may require that fitting subsystem 202 beassociated with a particular clinical trial), a user (e.g., thelicensing condition may require that fitting subsystem 202 be associatedwith a particular audiologist), a facility (e.g., the licensingcondition may require that fitting subsystem 202 be associated with aparticular clinic), a type of cochlear implant system (e.g., thelicensing condition may require that fitting subsystem 202 becommunicatively coupled to a particular type of sound processor orcochlear implant), a licensing key (e.g., the licensing condition mayrequire the input of a unique alpha-numeric key), a time period (e.g.,the licensing condition may specify a specific date on which a cochlearimplant fitting feature will be enabled or disabled), and/or any othersuitable information associated with fitting subsystem 202.

Feature control facility 308 may be configured to selectively enable ordisable each cochlear implant fitting feature of a cochlear implantfitting software package in accordance with a corresponding independentlicensing heuristic. For example, feature control facility 308 may beconfigured to detect whether one or more licensing conditions specifiedby a particular independent licensing heuristic have been satisfied, andenable or disable the corresponding cochlear implant fitting feature inresponse to the detection. To illustrate, if a particular independentlicensing heuristic specifies a condition that fitting subsystem 202 bephysically located within a particular geographic region (e.g., aparticular country), feature control facility 308 may be configured todetect a physical location of fitting subsystem 202 and determinewhether fitting subsystem 202 is physically located within theparticular geographic region. If fitting subsystem 202 is physicallylocated within the particular geographic region, feature controlfacility 308 may enable the corresponding cochlear implant fittingfeature. If fitting subsystem 202 is physically located outside of theparticular geographic, feature control facility 308 may disable thecorresponding cochlear implant fitting feature. Feature control facility308 may be configured to selectively enable or disable the cochlearimplant fitting features in any other suitable manner.

Feature control facility 308 may be further configured to dynamicallyadapt to changing circumstances associated with each independentlicensing heuristic. For example, feature control facility 308 may beconfigured to enable cochlear implant fitting features that werepreviously disabled and/or disable cochlear implant fitting featuresthat were previously enabled, in accordance with changing circumstancesaffecting the corresponding independent licensing heuristics. Toillustrate, in response to fitting subsystem 202 moving from a firstgeographic region to a second geographic region, feature controlfacility 308 may be configured to disable a first cochlear implantfitting feature associated with the first geographic region and enable asecond cochlear implant fitting feature associated with the secondgeographic region in accordance with corresponding independent licensingheuristics. Feature control facility 308 may be configured todynamically enable or disable cochlear implant fitting features in anyother suitable manner.

Additionally or alternatively, feature control facility 308 may beconfigured to override one or more independent licensing heuristics touse one or more corresponding cochlear implant fitting features. Toillustrate, feature control facility 308 may be configured to detectwhat cochlear implant fitting features have been previously used to fitsound processor 104 and/or cochlear implant 110. For example, featurecontrol facility 308 may be configured to receive data from soundprocessor 104 identifying one or more cochlear implant fitting featurespreviously used by an audiologist to fit sound processor 104 and/orcochlear implant 110 to a cochlear implant patient. In some examples,the one or more cochlear implant fitting features may be disabled onfitting subsystem 202 in accordance with one or more correspondingindependent licensing heuristics. In response to detecting that the oneor more disabled cochlear implant fitting features were previously usedto fit sound processor 104 and/or cochlear implant 110 to the patient,feature control facility 308 may be configured to override the one ormore corresponding independent licensing heuristics. After overridingthe one or more corresponding independent licensing heuristics, fittingsubsystem 202 may be configured to perform one or more fittingoperations in accordance with the one or more disabled cochlear implantfitting features. This may allow an audiologist to use fitting subsystem202 to perform the one or more fitting operations for the patient,despite a failure to satisfy the licensing conditions specified by theone or more corresponding independent licensing heuristics. In otherwords, fitting subsystem 202 may be configured to make an exception toconditions specified by an independent licensing heuristic in order toallow the patient to continue to have access to one or more fittingfeatures that were used previously to fit sound processor 104 and/orcochlear implant 110 to the patient. In response to a communicativedecoupling of fitting subsystem 202 from sound processor 104 (e.g.,after the one or more fitting operations are performed), fittingsubsystem 202 may restore the overridden independent licensingheuristics.

In some examples, feature control facility 308 may be further configuredto disable an enabled cochlear implant fitting feature after thecochlear implant fitting feature expires. For example, a particularcochlear implant fitting feature may be configured to expire after apredetermined period of time, after a predetermined number of uses, oron a predetermined date. To illustrate, the particular cochlear implantfitting feature may be associated with a clinical trial that ends on aparticular date or after a predetermined number of uses. Accordingly,feature control facility 308 may be configured to track the dates of useand/or number of uses of the particular cochlear implant fittingfeature. Once the clinical trial ends, feature control facility 308 maybe configured to disable the particular cochlear implant fittingfeature.

Feature control facility 308 may be configured to perform any othersuitable operations associated with the management of a cochlear implantfitting software package including a plurality of cochlear implantfitting features.

Storage facility 310 may be configured to maintain fitting feature data312 representative of one or more cochlear implant fitting features,licensing heuristic data 314 representative of one or more independentlicensing heuristics, patient data 316 representative of datadescriptive of or otherwise associated with one or more cochlear implantpatients, control parameter data 318 representative of one or morecontrol parameters, and program data 320 representative of one or moresound processing programs, any or all of which may be maintained withinone or more data sets. Storage facility 310 may be configured tomaintain additional or alternative data as may serve a particularimplementation.

FIG. 4 illustrates exemplary components of sound processor 104. As shownin FIG. 4, sound processor 104 may include a communication facility 402,a processing facility 404, and a storage facility 406, any or all ofwhich may be in communication with one another using any suitablecommunication technologies. Each of these facilities will now bedescribed in more detail.

Communication facility 402 may be configured to facilitate communicationbetween sound processor 104 and fitting subsystem 202. For example,communication facility 402 may be configured to facilitate electricalcoupling of sound processor 104 to a CPI device in order to communicatewith fitting subsystem 202. Communication facility 402 may be furtherconfigured to facilitate communication between sound processor 104 andcochlear implant 110. For example, communication facility 402 mayinclude transceiver components configured to wirelessly transmit data(e.g., control parameters and/or power signals) to cochlear implant 110and/or wirelessly receive data from cochlear implant 110.

Processing facility 404 may be configured to perform one or more signalprocessing heuristics on an audio signal presented to the patient. Forexample, processing facility 404 may perform one or more pre-processingoperations, spectral analysis operations, noise reduction operations,mapping operations, and/or any other types of signal processingoperations on a detected audio signal as may serve a particularimplementation. In some examples, processing facility 404 may generateand/or adjust one or more control parameters governing an operation ofcochlear implant 110 (e.g., one or more stimulation parameters definingthe electrical stimulation to be generated and applied by cochlearimplant 110). In some examples, processing facility 404 may beconfigured to operate in accordance with one or more sound processingprograms provided by fitting subsystem 202 and/or otherwise storedwithin storage facility 406.

Storage facility 406 may be configured to maintain fitting feature data408 representative of one or more cochlear implant fitting features usedto fit sound processor 104 to a patient and program data 410representative of one or more sound processing programs. Storagefacility 406 may be configured to maintain additional or alternativedata as may serve a particular implementation.

FIG. 5 illustrates an exemplary implementation 500 of fitting system200. In implementation 500, a fitting station 502 may be selectively andcommunicatively coupled to a BTE unit 504 by way of a CPI device 506.BTE unit 504 is merely exemplary of the many different types of soundprocessors that may be used in accordance with the systems and methodsdescribed herein. Fitting station 502 may be selectively andcommunicatively coupled to any other type of sound processor as mayserve a particular implementation.

Fitting station 502 may include any suitable computing device and/orcombination of computing devices and may be configured to perform one ormore of the fitting operations described herein. For example, fittingstation 502 may display one or more GUIs configured to facilitateselection of one or more measurements to perform using BTE unit 504,selection of one or more sound processing programs by which BTE unit 504operates, adjustment of one or more control parameters by which BTE unit504 operates, and/or any other fitting operation as may serve aparticular implementation. Fitting station 502 may be utilized by anaudiologist, a clinician, and/or any other user to fit one or morecochlear implants to a patient using BTE unit 504.

BTE unit 504 may be configured to selectively and communicatively coupleto a cochlear implant (e.g., cochlear implant 110). In this manner, BTEunit 504 may be configured to facilitate the fitting of the cochlearimplant by fitting station 502.

CPI device 506 may be configured to facilitate communication betweenfitting station 502 and BTE unit 504. In some examples, CPI device 506may be selectively and communicatively coupled to fitting station 502and/or BTE unit 504 by way of one or more ports included within fittingstation 502 and BTE unit 504.

FIG. 6 illustrates an exemplary method 600 of managing cochlear implantfitting software. While FIG. 6 illustrates exemplary steps according toone embodiment, other embodiments may omit, add to, reorder, and/ormodify any of the steps shown in FIG. 6. One or more of the steps shownin FIG. 6 may be performed by any component or combination of componentsof fitting subsystem 202 and/or fitting station 502.

In step 602, a cochlear implant fitting subsystem maintains datarepresentative of a cochlear implant fitting software package comprisinga plurality of cochlear implant fitting features. For example, storagefacility 310 may be configured to maintain the data representative ofthe cochlear implant fitting software package in any suitable manner,such as described herein.

FIG. 7 illustrates a block diagram of an exemplary cochlear implantfitting software package 700 (or simply “fitting software package 700”)that may be maintained by fitting subsystem 202. As shown, fittingsoftware package 700 may be configured to include a plurality ofcochlear implant fitting features 702-1 through 702-N (collectivelyreferred to herein as “fitting features 702”). Fitting features 702 mayinclude any suitable cochlear implant fitting features, such as thosedescribed herein. In addition, although FIG. 7 illustrates a certainnumber of fitting features 702, in further embodiments fitting softwarepackage 700 may include any number of fitting features 702 as may servea particular implementation.

Returning to FIG. 6, in step 604, the cochlear implant fitting subsystemmaintains data representative of a plurality of independent licensingheuristics corresponding to the plurality of cochlear implant fittingfeatures. In some examples, each independent licensing heuristic withinthe plurality of independent licensing heuristics may correspond to adifferent cochlear implant fitting feature within the plurality ofcochlear implant fitting features. Storage facility 310 may beconfigured to maintain the data representative of the plurality ofindependent licensing heuristics in any suitable manner, such asdescribed herein.

As shown in FIG. 7, fitting software package 700 may also include aplurality of independent licensing heuristics 704-1 through 704-N(collectively referred to herein as “licensing heuristics 704”). Asshown, each of licensing heuristics 704 may correspond to a differentfitting feature of fitting features 702 (e.g., licensing heuristic 704-1may correspond to fitting feature 702-1, licensing heuristic 704-2 maycorrespond to fitting feature 702-2, and so on). Licensing heuristics704 may include any suitable independent licensing heuristics, such asthose described herein. In addition, each of licensing heuristics 704may specify any suitable licensing condition(s), such as those describedherein.

Returning to FIG. 6, in step 606, the cochlear implant fitting subsystemselectively enables or disables each cochlear implant fitting feature inaccordance with the corresponding independent licensing heuristic. Forexample, feature control facility 308 may be configured to selectivelyenable or disable each cochlear implant fitting feature in any suitablemanner, such as described herein.

To illustrate, and returning to FIG. 7, fitting subsystem 202 may beconfigured to selectively enable or disable each of fitting features 702in accordance with licensing heuristics 704. For example, fittingsubsystem 202 may be configured to detect if one or more licensingconditions specified by licensing heuristic 704-1 are satisfied. Inresponse to a detection by fitting subsystem 202 that the one or morelicensing conditions specified by licensing heuristic 704-1 aresatisfied, fitting subsystem 202 may enable fitting feature 702-1. Inresponse to a detection that the one or more licensing conditionsspecified by licensing heuristic 704-1 are not satisfied, fittingsubsystem 202 may disable fitting feature 702-1. In this or a similarmanner, fitting feature 702-1 may be individually enabled or disabledindependently of other fitting features 702-2 through 702-N. The processmay be performed for each of fitting features 702-2 through 702-N inaccordance with licensing heuristics 704-2 through 704-N. In someexamples, fitting subsystem 202 may continue to selectively andindependently enable or disable fitting features 702 on an ongoingbasis, and dynamically adapt in response to any changed circumstancesaffecting licensing heuristics 704.

As mentioned above, fitting subsystem 202 may be configured to provide aGUI for display to a user. FIG. 8 includes an exemplary GUI 800 that maybe provided by fitting subsystem 202 for display to a user. As shown,GUI 800 may display information associated with fitting components(e.g., one or more sound processors and/or cochlear implants)communicatively coupled to fitting subsystem 202. In addition, GUI 800may display a listing 802 of cochlear implant fitting features. Forexample, listing 802 may include one or more cochlear implant featuresfrom a cochlear implant fitting software package maintained by fittingsubsystem 202. For each cochlear implant fitting feature included inlisting 802, listing 802 may display an associated status (e.g.,information indicating whether the cochlear implant fitting feature isenabled or disabled), an associated expiration (e.g., informationindicating whether the cochlear implant will expire and, if so, theconditions of the expiration), and an associated key (e.g., a uniquealpha-numeric key associated with the cochlear implant fitting feature).

In some examples, a user may use GUI 800 to add cochlear implant fittingfeatures to listing 802. For example, GUI 800 may include an option 804configured to facilitate the addition of a cochlear implant fittingfeature to listing 802. To illustrate, in response to a selection ofoption 804, GUI 800 may prompt the user for information identifying thecochlear implant fitting feature the user wishes to add to listing 802(e.g., GUI 800 may prompt the user for entry of a unique alpha-numerickey associated with the cochlear implant fitting feature the user wishesto add to listing 802). Once the cochlear implant fitting feature isadded to listing 802, GUI 800 may display a status, an expiration, and akey associated with the added cochlear implant fitting feature. In someexamples, adding a cochlear implant fitting feature to listing 802 mayfacilitate the enablement of the added cochlear implant fitting feature.For example, in response to detecting a user input of a uniquealpha-numeric key by way of GUI 800 and/or the satisfaction of one ormore corresponding licensing conditions, fitting subsystem 202 may beconfigured to enable the added cochlear implant fitting feature and makeit available for use by fitting subsystem 202.

Additionally or alternatively, GUI 800 may include an option 806configured to facilitate a removal of one or more cochlear implantfitting features from listing 802. For example, a user may select acochlear implant fitting feature from listing 802 and then select option806 to remove the selected cochlear implant fitting feature from listing802.

Fitting subsystem 202 may be additionally or alternatively configured toselectively override one or more independent licensing heuristics inaccordance with the fitting of a cochlear implant patient. Toillustrate, FIG. 9 shows an exemplary cochlear implant patient 900 beingfitted by the fitting components described in connection with FIG. 5. Asshown in FIG. 9, patient 900 may have a cochlear implant 902 associatedwith the patient's right ear. Cochlear implant 902 may be implanted inpatient 900 using any suitable technique as may serve a particularimplementation.

In some examples, BTE unit 504 may have been previously fitted topatient 900 using one or more cochlear implant fitting features that aredisabled on fitting station 502 (e.g., prior to being communicativelycoupled to fitting station 502, BTE unit 504 may have been fitted topatient 900 using another fitting station on which the one or morecochlear implant fitting features were enabled). Fitting station 502 maybe configured to detect that BTE unit 504 was previously fitted topatient 900 using one or more cochlear implant fitting features that aredisabled on fitting station 502. The detection may be performed in anysuitable manner as may serve a particular implementation. For example,fitting station 502 may detect and process fitting feature data (e.g.,fitting feature data 408) stored by BTE unit 504 and representative ofthe one or more cochlear implant fitting features. Additionally oralternatively, fitting feature data associated with the patient may beimported into fitting station 502 using an export file or the like.

The one or more cochlear implant fitting features may be disabled onfitting station 502 in accordance with one or more correspondingindependent licensing heuristics. In response to the detection that BTEunit 504 was previously fitted to patient 900 using the one or moredisabled cochlear implant fitting features, fitting station 502 mayoverride the one or more corresponding independent licensing heuristicsand perform one or more fitting operations in accordance with the one ormore disabled cochlear implant fitting features. As a result, fittingstation 502 may allow an audiologist to fit BTE unit 504 to patientusing the same cochlear implant fitting features that were previouslyused to fit BTE unit 504 to patient 900, despite the cochlear implantfitting features being otherwise disabled on fitting station 502.

FIG. 10 illustrates another exemplary method 1000 of managing cochlearimplant fitting software. While FIG. 10 illustrates exemplary stepsaccording to one embodiment, other embodiments may omit, add to,reorder, and/or modify any of the steps shown in FIG. 10. One or more ofthe steps shown in FIG. 10 may be performed by any component orcombination of components of fitting subsystem 202 and/or fittingstation 502.

In step 1002, a cochlear implant fitting subsystem maintains datarepresentative of a cochlear implant fitting software package comprisinga plurality of cochlear implant fitting features. The cochlear implantfitting subsystem may be configured to maintain the data representativeof the cochlear implant fitting software package in any suitable manner,such as described herein.

In step 1004, the cochlear implant fitting subsystem maintains datarepresentative of a plurality of independent licensing heuristicscorresponding to the plurality of cochlear implant fitting features. Thecochlear implant fitting subsystem may be configured to maintain thedata representative of the plurality of independent licensing heuristicsin any suitable manner, such as described herein.

In step 1006, the cochlear implant fitting subsystem detects asatisfaction of one or more licensing conditions specified by aparticular independent licensing heuristic. The particular independentlicensing heuristic may be one of the plurality of independent licensingheuristics. Cochlear implant fitting subsystem may be configured todetect the satisfaction of the one or more licensing conditionsspecified by the particular independent licensing heuristic in anysuitable manner, such as described herein.

In step 1008, the cochlear implant fitting subsystem enables aparticular cochlear implant fitting feature in response to the detectingthe satisfaction of the one or more licensing conditions. The particularcochlear implant fitting feature may correspond to the particularindependent licensing heuristic. The cochlear implant fitting subsystemmay be configured to enable the particular cochlear implant fittingfeature in any suitable manner, such as described herein.

In step 1010, the cochlear implant fitting subsystem performs one ormore cochlear implant fitting operations in accordance with theparticular cochlear implant fitting feature. The cochlear implantfitting subsystem may be configured to perform the one or more cochlearimplant fitting operations in any suitable manner, such as describedherein.

In certain embodiments, one or more of the components and/or processesdescribed herein may be implemented and/or performed by one or moreappropriately configured computing devices. To this end, one or more ofthe systems and/or components described above may include or beimplemented by any computer hardware and/or computer-implementedinstructions (e.g., software) embodied on a non-transitorycomputer-readable medium configured to perform one or more of theprocesses described herein. In particular, system components may beimplemented on one physical computing device or may be implemented onmore than one physical computing device. Accordingly, system componentsmay include any number of computing devices, and may employ any of anumber of computer operating systems.

In certain embodiments, one or more of the processes described hereinmay be implemented at least in part as instructions executable by one ormore computing devices. In general, a processor (e.g., a microprocessor)receives instructions, from a tangible computer-readable medium, (e.g.,a memory, etc.), and executes those instructions, thereby performing oneor more processes, including one or more of the processes describedherein. Such instructions may be stored and/or transmitted using any ofa variety of known non-transitory computer-readable media.

A non-transitory computer-readable medium (also referred to as aprocessor-readable medium) includes any non-transitory medium thatparticipates in providing data (e.g., instructions) that may be read bya computer (e.g., by a processor of a computer). Such a non-transitorymedium may take many forms, including, but not limited to, non-volatilemedia and/or volatile media. Non-volatile media may include, forexample, optical or magnetic disks and other persistent memory. Volatilemedia may include, for example, dynamic random access memory (“DRAM”),which typically constitutes a main memory. Common forms ofnon-transitory computer-readable media include, for example, a floppydisk, flexible disk, hard disk, magnetic tape, any other magneticmedium, a CD-ROM, DVD, any other optical medium, a RAM, a PROM, anEPROM, a FLASH-EEPROM, any other memory chip or cartridge, or any othernon-transitory medium from which a computer can read.

FIG. 11 illustrates an exemplary computing device 1100 that may beconfigured to perform one or more of the processes described herein. Asshown in FIG. 11, computing device 1100 may include a communicationinterface 1102, a processor 1104, a storage device 1106, and aninput/output (“I/O”) module 1108 communicatively connected via acommunication infrastructure 1110. While an exemplary computing device1100 is shown in FIG. 11, the components illustrated in FIG. 11 are notintended to be limiting. Additional or alternative components may beused in other embodiments. Components of computing device 1100 shown inFIG. 11 will now be described in additional detail.

Communication interface 1102 may be configured to communicate with oneor more computing devices. Examples of communication interface 1102include, without limitation, a wired network interface (such as anetwork interface card), a wireless network interface (such as awireless network interface card), a modem, and any other suitableinterface. Communication interface 1102 may additionally oralternatively provide such a connection through, for example, a localarea network (such as an Ethernet network), a personal area network, atelephone or cable network, a satellite data connection, a dedicatedURL, or any other suitable connection. Communication interface 1102 maybe configured to interface with any suitable communication media,protocols, and formats, including any of those mentioned above.

Processor 1104 generally represents any type or form of processing unitcapable of processing data or interpreting, executing, and/or directingexecution of one or more of the instructions, processes, and/oroperations described herein. Processor 1104 may direct execution ofoperations in accordance with one or more applications 1112 or othercomputer-executable instructions such as may be stored in storage device1106 or another non-transitory computer-readable medium.

Storage device 1106 may include one or more data storage media, devices,or configurations and may employ any type, form, and combination of datastorage media and/or device. For example, storage device 1106 mayinclude, but is not limited to, a hard drive, network drive, flashdrive, magnetic disc, optical disc, random access memory (“RAM”),dynamic RAM (“DRAM”), other non-volatile and/or volatile data storageunits, or a combination or sub-combination thereof. Electronic data,including data described herein, may be temporarily and/or permanentlystored in storage device 1106. For example, data representative of oneor more executable applications 1112 (which may include, but are notlimited to, one or more of the software applications described herein)configured to direct processor 1104 to perform any of the operationsdescribed herein may be stored within storage device 1106. In someexamples, data may be arranged in one or more databases residing withinstorage device 1106.

I/O module 1108 may be configured to receive user input and provide useroutput and may include any hardware, firmware, software, or combinationthereof supportive of input and output capabilities. For example, I/Omodule 1108 may include hardware and/or software for capturing userinput, including, but not limited to, a keyboard or keypad, a touchscreen component (e.g., touch screen display), a receiver (e.g., an RFor infrared receiver), and/or one or more input buttons.

I/O module 1108 may include one or more devices for presenting output toa user, including, but not limited to, a graphics engine, a display(e.g., a display screen, one or more output drivers (e.g., displaydrivers), one or more audio speakers, and one or more audio drivers. Incertain embodiments, I/O module 1108 is configured to provide graphicaldata to a display for presentation to a user. The graphical data may berepresentative of one or more graphical user interfaces and/or any othergraphical content as may serve a particular implementation.

In some examples, any of the facilities described herein may beimplemented by or within one or more components of computing device1100. For example, one or more applications 1112 residing within storagedevice 1106 may be configured to direct processor 1104 to perform one ormore processes or functions associated with communication facility 302,user interface facility 304, fitting facility 306, feature controlfacility 308, communication facility 402, and/or processing facility404. Likewise, storage facility 310 and/or storage facility 406 may beimplemented by or within storage device 1106.

In the preceding description, various exemplary embodiments have beendescribed with reference to the accompanying drawings. It will, however,be evident that various modifications and changes may be made thereto,and additional embodiments may be implemented, without departing fromthe scope of the invention as set forth in the claims that follow. Forexample, certain features of one embodiment described herein may becombined with or substituted for features of another embodimentdescribed herein. The description and drawings are accordingly to beregarded in an illustrative rather than a restrictive sense.

What is claimed is:
 1. A method comprising: maintaining, by a cochlearimplant fitting subsystem, data representative of a licensing heuristic;maintaining, by the cochlear implant fitting subsystem, datarepresentative of a cochlear implant fitting software package comprisinga cochlear implant fitting feature that is disabled in accordance withthe licensing heuristic; detecting, by the cochlear implant fittingsubsystem, that the cochlear implant fitting subsystem iscommunicatively coupled to a sound processor previously fitted using thedisabled cochlear implant fitting feature; overriding, by the cochlearimplant fitting subsystem in response to the detecting of thecommunicative coupling, the licensing heuristic corresponding to thedisabled cochlear implant fitting feature; and performing, by thecochlear implant fitting subsystem, one or more cochlear implant fittingoperations in accordance with the one or more disabled cochlear implantfitting feature.
 2. The method of claim 1, wherein the cochlear implantfitting software package further comprises an additional cochlearimplant fitting feature, and wherein the method further comprises:maintaining, by the cochlear implant fitting subsystem, datarepresentative of an additional licensing heuristic corresponding to theadditional cochlear implant fitting feature and specifying one or morelicensing conditions; detecting, by the cochlear implant fittingsubsystem, whether the one or more licensing conditions are satisfied;selectively enabling, by the cochlear implant fitting subsystem, theadditional cochlear implant fitting feature in accordance with theadditional licensing heuristic if the one or more licensing conditionsare satisfied; and selectively disabling, by the cochlear implantfitting subsystem, the additional cochlear implant fitting feature inaccordance with the additional licensing heuristic if the one or morelicensing conditions are not satisfied.
 3. The method of claim 2,wherein: the one or more licensing conditions require that the cochlearimplant fitting subsystem be physically located within a predeterminedgeographic region; and the detecting comprises detecting whether thecochlear implant fitting subsystem is physically located within thepredetermined geographic region.
 4. The method of claim 2, wherein: theone or more licensing conditions require that the cochlear implantfitting subsystem be associated with a particular clinical trial; andthe detecting comprises detecting whether the cochlear implant fittingsubsystem is associated with the particular clinical trial.
 5. Themethod of claim 2, wherein: the one or more licensing conditions requireentry by a user of a unique alpha-numeric key; and the detectingcomprises detecting whether the user has input of the uniquealpha-numeric key.
 6. The method of claim 2, wherein the one or morelicensing conditions are satisfied, and wherein the method furthercomprises disabling, by the cochlear implant fitting subsystem, theadditional cochlear implant fitting feature a predetermined period oftime subsequent to the enabling of the additional cochlear implantfitting feature.
 7. The method of claim 2, wherein the one or morelicensing conditions are satisfied, and wherein the method furthercomprises disabling, by the cochlear implant fitting subsystem, theadditional cochlear implant fitting feature on a predetermined datesubsequent to the enabling of the additional cochlear implant fittingfeature.
 8. The method of claim 2, wherein the one or more licensingconditions are satisfied, and wherein the method further comprisingperforming, by the cochlear implant fitting subsystem, one or morecochlear implant fitting operations in accordance with the additionalcochlear implant fitting feature after the enabling of the additionalcochlear implant fitting feature.
 9. The method of claim 1, furthercomprising: detecting, by the cochlear implant fitting subsystem, acommunicative decoupling of the cochlear implant fitting subsystem fromthe sound processor; and restoring, by the cochlear implant fittingsubsystem in response to the detecting the communicative decoupling, thelicensing heuristic.
 10. The method of claim 2, wherein the selectivelyenabling or the disabling of the additional cochlear implant fittingfeature comprises dynamically enabling or disabling the additionalcochlear implant fitting feature in accordance with a change associatedwith the additional licensing heuristic.
 11. The method of claim 2,embodied as computer-executable instructions on at least onenon-transitory computer-readable medium.
 12. The method of claim 2,wherein the one or more licensing conditions are satisfied, and whereinthe method further comprises disabling, by the cochlear implant fittingsubsystem, the additional cochlear implant fitting feature in response apredetermined number of uses of the additional cochlear implant fittingfeature subsequent to the enabling of the additional cochlear implantfitting feature.
 13. The method of claim 2, wherein the cochlear implantfitting software package further comprises a second additional cochlearimplant feature, and wherein the method further comprises: maintaining,by the cochlear implant fitting subsystem, data representative of asecond additional licensing heuristic corresponding to the secondadditional cochlear implant fitting feature and specifying one or moreadditional licensing conditions; and detecting, by the cochlear implantfitting subsystem, whether the one or more additional licensingconditions are satisfied; selectively enabling, by the cochlear implantfitting subsystem, the second additional cochlear implant fittingfeature in accordance with the second additional licensing heuristic ifthe one or more licensing additional conditions are satisfied; andselectively disabling, by the cochlear implant fitting subsystem, thesecond additional cochlear implant fitting feature in accordance withthe second additional licensing heuristic if the one or more additionallicensing conditions are not satisfied.